I see that this thread is several years old... I'm having the same problem now with Xcode 14.2 under macOS 13.1 Ventura. I've tried the terminal commands above with no luck. xcode-select --install tells me that the command line tools are already installed -- which makes sense, since I installed the Xcode 14.2 command line tools separately after installing Xcode itself. I downloaded command line tools for macOS 10.14 and ran "open /Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg" which ran an installer. After restarting my Mac, I still get the following error when compiling for a macOS 10.13 target: 'CoreFoundation/CFString.h' file not found In Xcode settings > Locations I have the Command Line Tools set to Xcode 14.2, which is the only available option. Targeting macOS 10.14 or higher works fine, but I also need a build for 10.13. I don't know if this is related, but I also get an error in __config line 1123 'No thread API' Any suggestions would be much appreciated.

I had some trouble creating the keychain profile, so I'll share some tips I found in getting it to work. First, for your team ID, don't enter the name as entered in "Development Team" in the signing section of your Xcode project settings. Hover over the name and use the 10-character code that appears there. When the terminal asks for your app-specific password, I wasn't able to paste it. I had to type the whole thing, and do it blindly since the terminal doesn't show you what you're typing. Once the keychain profile was created, the terminal command worked great. I like how the --wait option gives confirmation of success right in the terminal window, rather than having to wait for an email.

Thanks! I suspect macOS is blocking it, though. In trying to find how to implement that in a non-typical Mac app (I write plugins for Adobe Illustrator using their c++ SDK and Hot Door's CORE), I found that macOS often blocks keyboard activity. In Ventura's System Settings > Privacy & Security > Input Monitoring I added Adobe Illustrator 2023 to the list of applications allowed to monitor the keyboard. I've been using a CORE function to monitor key presses, which has worked well until recently, and still works well for others with an older OS -- I suspect CORE already implemented CGEventSourceKeyState so my workaround is not likely to work. Where else in macOS Ventura could those keystrokes be blocked?